…80750)

The timestamps are only used by ansible-test, not the junit callback, so this change only impacts ansible-test.
(cherry picked from commit fd34126)

Co-authored-by: Matt Clay <matt@mystile.com>

…80750)

The timestamps are only used by ansible-test, not the junit callback, so this change only impacts ansible-test.
(cherry picked from commit fd34126)

Co-authored-by: Matt Clay <matt@mystile.com>

…80750)

The timestamps are only used by ansible-test, not the junit callback, so this change only impacts ansible-test.
(cherry picked from commit fd34126)

Co-authored-by: Matt Clay <matt@mystile.com>

…80750)

The timestamps are only used by ansible-test, not the junit callback, so this change only impacts ansible-test.
(cherry picked from commit fd34126)

Co-authored-by: Matt Clay <matt@mystile.com>

…80758)

The timestamps are only used by ansible-test, not the junit callback, so this change only impacts ansible-test.

(cherry picked from commit fd34126)

…80759)

The timestamps are only used by ansible-test, not the junit callback, so this change only impacts ansible-test.

(cherry picked from commit fd34126)

…80760)

The timestamps are only used by ansible-test, not the junit callback, so this change only impacts ansible-test.

(cherry picked from commit fd34126)

…80757)

The timestamps are only used by ansible-test, not the junit callback, so this change only impacts ansible-test.

(cherry picked from commit fd34126)